test: document ctags false positive on JS prototype calls - #2196
Merged
Conversation
Fixes a bug where languages explicitly opting out of class extraction (class_start: None) were falling back to a generic regex and incorrectly finding classes in embedded snippets (e.g., m4 finding C structs in autoconf tests). Resolves #1925
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #2194
This PR adds a note to
tests/tools/ctags_reader.pydocumenting a parser limitation in ctags where function calls on prototype methods (e.g.Material.prototype.copy.call(...)) are falsely tagged as method declarations.